Changes

With the specification on the plugin definition of runon the BoefjeScheduler should be able to discern between task that needs to run once or that a schedule needs to be created, and based on what type of mutation (CREATE , UPDATE).

When a schedule or when a task needs to be run is laid out in this table #3879 (comment)

Note that the create_schedule attribute on a Scheduler always takes precedence. When this is set to False under no circumstances a schedule will be created. As is the case with the NormalizerScheduler.

Reviewer notes

Tests for the outcomes of the mentioned table should be made. This is as of yet untested, but can be reviewed, and qa'ed.

Issue link

Closes #3879

QA notes

Should be able to work with the following pr #3901

Reference this table #3879 (comment)

These paths should be tested

Code Checklist

• All the commits in this PR are properly PGP-signed and verified.
• This PR only contains functionality relevant to the issue.
• I have written unit tests for the changes or fixes I made.
• I have checked the documentation and made changes where necessary.
• I have performed a self-review of my code and refactored it to the best of my abilities.

• Tickets have been created for newly discovered issues.
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have included comments in the code to elaborate on what is not self-evident from the code itself, including references to issues and discussions online, or implicit behavior of an interface.

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.